Minutes, IBIS Quality Committee 05 May 2015 11:00-12:00 EST (08:00-09:00 PST) ROLL CALL eASIC: David Banas Ericsson: Anders Ekholm Intel: Michael Mirmak Eugene Lim IO Methodology * Lance Wang Signal Integrity Software * Mike LaBonte Teraspeed Labs: * Bob Ross Everyone in attendance marked by * NOTE: "AR" = Action Required. -----------------------MINUTES --------------------------- Mike LaBonte conducted the meeting. Call for IBIS related patent disclosures: - None Call for opens: - None ARs: - Mike update HTML IBISCHK message files and send to Bob and Lance. - Done. - Mike recover percent format specifications in spreadsheet. - No new progress, this will be next. - Mike add comments to CMPNT, DLY, MSPEC sections. - No new progress. - Lance add comments to EBD section. - No new progress. - Bob add comments to CIRCUIT section. - No new progress. Parser development: - Bob showed a list of checks related to [Merged Pins]. - Bob: We have been calling this BIRD175 but it probably will be BIRD176 now. - These are all syntax requirements, producing IBISCHK errors. - Checks 1 through 7 can be done on a separate .pkg file. - Mike: The [Pin Mapping] example could have more pins to show buses. - Bob: I'll add that later. - This contains suggested error message language. - Mike: We should designate the messages that will have a line number. IBISCHK Message Comments: - Mike: - Lance: Those should be separate. - Bob: That check would be later than version 2.1. - Mike: Many of these are ifdefed out. - Lance: Could be processed out? - Mike: gcc -E can do that. - We would have to be careful to define everyting used for compile. - Bob: We need to keep listing these old messages. - Mike: The script could generate comments for checks that are ifdefed out. - Mike: There is a code quality issue if so much code is commented out. - Version control would have allowed us to delete unused code. - Bob: Where would the master copies. IBISCHK DLL checking: - Bob: - Lance: Could a program just call the DLL? - It should not be that complicated. - Mike: If the AMI has GetWave_Exists=True then it would be an error if AMI_GetWave is absent. - Lance: Checking for existence of function might be all we can do. - Mike: We could check 32/64 bit. - We could check platform too. - Lance: we could check for dependencies too. - Function parameters would be hard to check. - Mike: We could check for -1 after clock_times. - Also see if impulse_matrix has been modified if Init_Returns_Impule=True. - Lance: Is there public source code for loading these DLLs? - Mike: No, but it takes just a few lines of code. - David Banas' Python tool started this conversation. - But it should be very easy to add to IBISCHK. - The code is just slightly different across platforms. - Mike showed the Algrothmic Model section of IBIS 6.0. - Mike: The checks should be based on requirements in this section. - Lance: It would be good to check that the function signatures have been implemented correctly. - Mike showed contents of the Cadence and SiSoft public AMI evaluation kits. - Lance: Do they include source code? - We found source code for a Cadence RX model and a SiSoft TX model. AR: Mike LaBonte create list of possible DLL checks for IBISCHK. Meeting ended: 11:53 Next meeting May 12